Skip to content

Update check-answers.html - #1071

Merged
maddie-broxup merged 3 commits into
mainfrom
maddie-broxup-patch-6
Jul 8, 2025
Merged

Update check-answers.html#1071
maddie-broxup merged 3 commits into
mainfrom
maddie-broxup-patch-6

Conversation

@maddie-broxup

@maddie-broxup maddie-broxup commented Jul 7, 2025

Copy link
Copy Markdown
Contributor

Content tweaks to reflect new service name from submit to provide

Description

Content tweaks to reflect new service name from submit to provide

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Related Tickets & Documents

#1013

  • Closes #

QA Instructions, Screenshots, Recordings

Before

Before screenshot here

After

After screenshot here

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above.

  • Yes
  • No, and this is why: Please replace this line with details on why tests have not been included
  • I need help with writing tests

QA sign off

  • Code has been checked and approved
  • Design has been checked and approved
  • Product and business logic has been checked and proved

[optional] Are there any post-deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

Summary by CodeRabbit

  • Style
    • Updated user-facing text to replace "submit" with "provide" throughout the dataset submission page for improved clarity.

Content tweaks to reflect new service name from submit to provide
@coderabbitai

coderabbitai Bot commented Jul 7, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This change updates the wording in the check-answers.html template, replacing all instances of "submit" with "provide" in the context of dataset submission. No changes were made to the logic, structure, or data handling—only the user-facing text was modified.

Changes

File(s) Change Summary
src/views/submit/check-answers.html Replaced all instances of "submit" with "provide" in user-facing text

Possibly related PRs

  • Update get-started.html #1068: Updates user-facing text to replace "submit" with "provide" in HTML templates for dataset submission, focusing on wording changes only.

Suggested reviewers

  • paris-dp

Poem

A bunny hopped through fields of code,
Swapping "submit" for "provide" as it strode.
No logic disturbed, just words rearranged,
The dataset journey, gently rephrased.
With every hop, the message grew clear—
"Provide your data," so users now hear!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions

github-actions Bot commented Jul 7, 2025

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 66.41% 5956 / 8968
🔵 Statements 66.41% 5956 / 8968
🔵 Functions 64.87% 253 / 390
🔵 Branches 79.7% 758 / 951
File CoverageNo changed files found.
Generated in workflow #1106 for commit 381d70a by the Vitest Coverage Report Action

@stevenjmesser stevenjmesser left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
src/views/submit/check-answers.html (4)

28-30: Improve heading phrasing and keep service-name consistent

“Check your answers before providing your dataset” reads a little awkwardly; GOV.UK style tends to prefer the construction “before you provide”.
While touching this block, also consider aligning the service-name with the heading by changing the earlier serviceType value from “Submit” to “Provide” for consistency across analytics, breadcrumbs, etc.

-      Check your answers before providing your dataset
+      Check your answers before you provide your dataset

139-141: Minor wording tweak for clarity

“Now provide your dataset” is succinct, but GOV.UK headings usually start with a verb followed by the object: “Provide your dataset now” or simply “Provide your dataset”.
Consider the shorter variant for better scannability.

-      Now provide your dataset
+      Provide your dataset

143-145: Reduce repetition in the confirmation sentence

The sentence repeats “providing / provide” twice. A lighter construction keeps the same meaning:

-      By providing this dataset you are confirming that, to the best of your knowledge, the details you are providing are correct.
+      By providing this dataset, you confirm that, to the best of your knowledge, the details are correct.

149-152: Button label could be more explicit

“Accept and provide” may be unclear to users unfamiliar with the new terminology. A more explicit action such as “Provide dataset” mirrors the heading and avoids ambiguity.

-        text: "Accept and provide",
+        text: "Provide dataset",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 701d64c and de72115.

📒 Files selected for processing (1)
  • src/views/submit/check-answers.html (2 hunks)
🧰 Additional context used
🧠 Learnings (1)
src/views/submit/check-answers.html (1)
Learnt from: DilwoarH
PR: digital-land/submit#1043
File: src/controllers/issueDetailsController.js:83-88
Timestamp: 2025-06-30T22:12:04.103Z
Learning: The datasette service in digital-land/submit only accepts string queries, not parameterized queries with text/values objects. SQL interpolation with trusted data sources is the accepted pattern.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: test
  • GitHub Check: run-tests / test

@maddie-broxup
maddie-broxup merged commit a0bc8a3 into main Jul 8, 2025
5 checks passed
@maddie-broxup
maddie-broxup deleted the maddie-broxup-patch-6 branch July 8, 2025 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants